Multi Stepper TB67S109 Click
Multi Stepper TB67S109 Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.
Click Library
- Author : Stefan Filipovic
- Date : Feb 2022.
- Type : I2C type
Software Support
Example Description
This example demonstrates the use of the Multi Stepper TB67S109 Click board by driving the motor in both directions for a desired number of steps.
Example Libraries
- MikroSDK.Board
- MikroSDK.Log
- Click.MultiStepperTB67S109
Example Key Functions
- multisteppertb67s109_cfg_setup Config Object Initialization function.
void multisteppertb67s109_cfg_setup(multisteppertb67s109_cfg_t *cfg)
Multi Stepper TB67S109 configuration object setup function.
Multi Stepper TB67S109 Click configuration object.
Definition multisteppertb67s109.h:210
- multisteppertb67s109_init Initialization function.
err_t multisteppertb67s109_init(multisteppertb67s109_t *ctx, multisteppertb67s109_cfg_t *cfg)
Multi Stepper TB67S109 initialization function.
Multi Stepper TB67S109 Click context object.
Definition multisteppertb67s109.h:187
- multisteppertb67s109_default_cfg Click Default Configuration function.
err_t multisteppertb67s109_default_cfg(multisteppertb67s109_t *ctx)
Multi Stepper TB67S109 default configuration function.
- multisteppertb67s109_set_step_mode This function sets the step mode resolution settings.
err_t multisteppertb67s109_set_step_mode(multisteppertb67s109_t *ctx, uint8_t mode)
Multi Stepper TB67S109 set step mode function.
- multisteppertb67s109_drive_motor This function drives the motor for the specific number of steps at the selected speed.
void multisteppertb67s109_drive_motor(multisteppertb67s109_t *ctx, uint32_t steps, uint8_t speed)
Multi Stepper TB67S109 driver motor function.
- multisteppertb67s109_set_direction This function sets the motor direction by setting the AN pin logic state.
void multisteppertb67s109_set_direction(multisteppertb67s109_t *ctx, uint8_t dir)
Multi Stepper TB67S109 set direction function.
Application Init
Initializes the driver and performs the Click default configuration.
{
log_cfg_t log_cfg;
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
#define MULTISTEPPERTB67S109_MAP_MIKROBUS(cfg, mikrobus)
MikroBUS pin mapping.
Definition multisteppertb67s109.h:170
void application_init(void)
Definition main.c:30
@ MULTISTEPPERTB67S109_ERROR
Definition multisteppertb67s109.h:232
Application Task
Drives the motor clockwise for 200 steps and then counter-clockiwse for 100 steps with 2 seconds delay before changing the direction. Each step will be logged on the USB UART where you can track the program flow.
{
log_printf ( &logger, " Move 200 steps clockwise \r\n\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
log_printf ( &logger, " Move 100 steps counter-clockwise \r\n\n" );
Delay_ms ( 1000 );
Delay_ms ( 1000 );
}
#define MULTISTEPPERTB67S109_SPEED_FAST
Definition multisteppertb67s109.h:141
#define MULTISTEPPERTB67S109_DIR_CCW
Definition multisteppertb67s109.h:111
#define MULTISTEPPERTB67S109_DIR_CW
Multi Stepper TB67S109 direction setting.
Definition multisteppertb67s109.h:110
void application_task(void)
Definition main.c:66
Application Output
This Click board can be interfaced and monitored in two ways:
- Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
- UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Additional Notes and Information
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.